We now only need to support doing this in the CLI.

It is 2.8.2, not 2.7.3.

Mergeback v2.1.32 refs/heads/releases/v2 into main

This is now covered by `codescanning-config-cli.yml`.

These are covered by `codeql.yml`, which runs across all latest runner
images.

These are tested by `multi-language-autodetect.yml`

These are covered by `autobuild-action.yml`.

Testing SARIF compatibility is covered by `codeql.yml`.

We don't need to test runner functionality now since the runner is only
used in PR checks, and `extractor-ram-threads.yml` covers the Action
case.

Co-authored-by: Henry Mercer <henry.mercer@me.com>

We could move everything into `util`, but in some ways it is nice having
a file dedicated to Actions related utilities.

…CTOR_GO_BUILD_TRACING` for custom builds (#1322)

Co-authored-by: Henry Mercer <henry.mercer@me.com>

Also update query ID prefixes for C# and Ruby

Update lockfiles to v3

…ixes

Add Swift file baseline info to expected list

Read CODE_SCANNING_REF env variable

Delete the runner, part 1

…ire-cli-2.6.3

Delete the runner, part 2

Given that the GITHUB_REF is a protected variable, we want to prefer it to
CODE_SCANNING_REF. This should prevent accidentally overwriting these values.
The logic is a bit more involved, as I think it makes sense to raise the error
about GITHUB_REF not being set, rather than mentioning CODE_SCANNING_REF if
both are not set.

Bump minimum CodeQL bundle version to 2.6.3

Prefer GITHUB_REF to CODE_SCANNING_REF